Skip to content

[Storage] [STG 103/104] Changelog updates + date for release#48006

Open
weirongw23-msft wants to merge 1 commit into
Azure:feature/storage/stg103-104from
weirongw23-msft:weirongw23/103-104-changelogs
Open

[Storage] [STG 103/104] Changelog updates + date for release#48006
weirongw23-msft wants to merge 1 commit into
Azure:feature/storage/stg103-104from
weirongw23-msft:weirongw23/103-104-changelogs

Conversation

@weirongw23-msft

Copy link
Copy Markdown
Member

Updated the release date (for now) to 2026-07-21.

Two questions:

  1. In Datalake, there are no changes other than _shared folder changes from the Unique Put Block IDs feature. Is it fine to leave blank? We've had releases where Features Added were left blank.
  2. In Queue, there's the TypeSpec changes. Because it's largely generated code, Features Added, Bugs Fixed are both weird. We could potentially consider specifying this in Other Changes, but again none that directly affect the users because they're generated code.

@github-actions github-actions Bot added the Storage Storage Service (Queues, Blobs, Files) label Jul 11, 2026
@weirongw23-msft weirongw23-msft marked this pull request as ready for review July 11, 2026 13:13
`BlobClient` upload operations (`stage_block`, `stage_block_from_url`, `upload_page`,
`upload_pages_from_url`, `append_block`, `append_block_from_url`, `upload_blob`, and
`upload_blob_from_url`) in addition to `content_md5` when a content MD5 is
provided with the request.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add an "Other Changes" section about the block IDs. Something like "Partitioned upload via upload_blob with Block Blobs will now generate random, unique block ids for each block rather than using a sequential count. The length of the new block ids will be the same as previous versions to ensure backwards compatibility."

## 12.26.0b1 (Unreleased)
## 12.26.0b1 (2026-07-21)

### Features Added

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about - Added support for service version 2026-10-06. That would give you something to put here.

## 12.18.0b1 (Unreleased)
## 12.18.0b1 (2026-07-21)

### Features Added

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Added support for service version 2026-10-06.

service responses.
- Added a new `FileRange` model with `start`, `end`, and `cleared` properties.

### Other Changes

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's put an entry here and in Queue for the TypeSpec migration. "Migrated generated code to use new TypeSpec generator." - This won't mean much to customers but is good to know for internal use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Storage Storage Service (Queues, Blobs, Files)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants